Full-Duplex Bi-Directional Communication Over a Remote Procedure Call Based Communications Protocol, and Applications Thereof

ABSTRACT

Systems and methods for reducing the cost but increasing the performance caused in streaming data between a client and a server are described herein. Embodiments of the present invention relate to reducing the cost but increasing the performance by the traditional data streaming where two TCP connections, one for each direction of traffic is used. Further embodiments allow a server in communication with one or more clients using a RPC based communication protocol to bi-directional stream not on two TCP connections but a single TCP connection. In one embodiment, this is achieved, by transmitting from the client to the server an initial handshake. If the server receives the handshake, then the client streams a request stream to the server and the server streams a response stream to the client simultaneously over the same single TCP connection establishing full-duplex streaming.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a U.S. Nonprovisional Application which claims thebenefit of U.S. Provisional Application No. 61/411,321 filed on Nov. 8,2010, which is incorporated herein by reference in its entirety.

BACKGROUND

Hypertext Transfer Protocol (HTTP) is a stateless, Remote Procedure Call(RPC) style protocol which requires communication between client andserver and follows a strict request-response pattern. HTTP streams datafrom either client to server or server to client. Currently,bi-directional streaming from client to server and server to clientrequires two transmission control protocol (TCP) connections to streamdata between the client and server separately. A first TCP connection isused by the client to stream a request to the server while a second TCPconnection is used by the server to stream a response to the client.

For example, for client to server communication, methods include aHanging GET, long polling, and polling. The Hanging GET method includesa pending RPC protocol that allows the server to stream response data tothe client at any time. The request from the client does not include aninitial handshake request and the request does not contain data. Thelong polling method is similar to the Hanging GET method but theresponse from the server is terminated for each piece of data that theserver sends to the client. The client is required to initiate a new RPCprotocol to receive the next message. The polling method requires theclient to poll the server by generating a new RPC protocol periodicallyto receive data from the server.

For example, for server to client communication, methods include sendingone request at a time and a long-lived request. The sending of onerequest at a time method requires that the first request be sent as ahandshake request that carries application-layer protocol semantics. Thelong-lived request method requires that a single RPC protocol continuesto send request data to the server. When the streaming of request datais finished, the RPC protocol is completed.

These dual TCP connection approaches are bi-directional but are notfull-duplex. Such dual TCP connection approaches incur added costs thatin turn introduces added overhead. The added TCP connection consumessystem and network resources. The request streaming and responsestreaming that each occur on different TCP connections require that bothconnections remain activated. This adds additional network traffic. Thedual TCP connection approach also makes HTTP insufficient to be used asa standalone protocol while requiring additional application-levelprotocols to handle the two connections.

BRIEF SUMMARY

Embodiments relate to data streaming capabilities between a server and aclient. In a first embodiment, a computer implemented method provides afull-duplex capable client a capability to establish a full-duplexbi-directional communication stream over a remote procedure call basedcommunication protocol by way of a single protocol connection.Full-duplex communication is initiated over a single protocol connectionbetween the full-duplex capable client and a server via a network wherethe full-duplex capable client is configured to engage the server bysending an initial handshake to the server. A client request stream isstreamed by the fall-duplex client to the server following an acceptanceof the initial handshake by the server via the network over the singleprotocol connection. A response stream is accepted from the server overthe single protocol connection while the full-duplex capable clientstreams the client request stream over the single protocol connection.The full-duplex bi-directional communication stream is enabled over theremote procedure call based communication protocol when the clientrequest stream and the response stream communicate over the singleprotocol connection simultaneously.

In a second embodiment, a system provides a full-duplex capable serverwith the capability to establish a full-duplex bi-directionalcommunication stream over a remote procedure call based communicationprotocol by way of a single protocol connection. A server connectionmodule finalizes an initialization of full-duplex communication over asingle protocol connection between the full-duplex capable server and aclient via a network where the full-duplex capable server is configuredto accept an initial handshake from the client. A server acceptancemodule accepts a request stream over the single protocol connection. Aserver delivery module transfers the request stream received by thefull-duplex capable server to a server application. A server streamingmodule streams a server response stream to the client that includes anapplication response to the request stream by the application via thenetwork over the single protocol connection. A server enablement moduleenables a full-duplex bi-directional communication stream over theremote procedure call based communication protocol when the serverresponse stream and the request stream use the single protocolconnection simultaneously.

Further embodiments, features, and advantages, as well as the structureand operation of the various embodiments, are described in detail belowwith reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

Embodiments are described with reference to the accompanying drawings.In the drawings, like reference numbers may indicate identical orfunctionally similar elements.

FIG. 1 illustrates a full-duplex bi-directional communication system,according to an embodiment;

FIG. 2 illustrates a full-duplex bi-directional communication systemincluding a client application and a server application, according to anembodiment;

FIG. 3 illustrates a client server f bi-directional communicationprotocol, according to an embodiment;

FIG. 4 illustrates a full-duplex bi-directional communication systemarchitecture, according to an embodiment;

FIG. 5 illustrates a flow chart illustrating an exemplary aspect ofoperation for a full-duplex capable client, according to an embodiment.

FIG. 6 illustrates a flow chart illustrating an exemplary aspect ofoperation for a full-duplex capable server, according to an embodiment;

DETAILED DESCRIPTION

Full-duplex bi-directional communication provides a capability for aserver to stream data to a client and a client to stream data to aserver simultaneously over a single protocol connection. In the DetailedDescription herein, references to “one embodiment”, “an embodiment”, “anexample embodiment”, etc., indicate that the embodiment described mayinclude a particular feature, structure, or characteristic, but everyembodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic may be described in connection with anembodiment, it may be submitted that it may be within the knowledge ofone skilled in the art to effect such feature, structure, orcharacteristic in connection with other embodiments whether or notexplicitly described.

Overview

FIG. 1 illustrates a client-server network system 100 in whichembodiments, or portions thereof, may be implemented. System 100includes a full-duplex capable server 102, a full-duplex capable client112, a network 108, and a single TCP connection 130.

Generally speaking, one or more full-duplex capable clients 112 connectto a full-duplex capable server 102 over a network 108. In embodiments,a full-duplex capable server 102 may include a conventional web server,email server, or file transfer server modified according to theteachings in this disclosure. Full-duplex capable server 102 may be adevice that includes at least one processor, at least one memory, and atleast one network interface.

Full-duplex capable client 112 may be a device that includes at leastone processor, at least one memory, and at least one network interface.For example, full-duplex capable client 112 may be implemented on apersonal computer, handheld computer, personal digital assistant, smartphone, a mobile telephone, a game console, a set-top box, and the like.

Network 108 may include one or more networks, such as the Internet. Insome examples, network 108 may include one or more wide area networks(WAN) or local area networks (LAN). Network 108 may include one or morenetwork technologies such as Ethernet, Fast Ethernet, Gigabit Ethernet,a variant of the IEEE 802.11 standard such as WiFi, and the like.Communication over network 108 takes place using one or more networkcommunication protocols including reliable streaming protocols such asTCP. These examples are illustrative and not intended to limit thepresent disclosure.

Full-duplex capable client 112 and full-duplex capable server 102 may bein data communication over network 108 using a protocol such as TCP. TCPis a reliable streaming protocol, also known as a guaranteed deliveryprotocol or connection-oriented protocol, where “reliable” and“guaranteed delivery” refer to the nature of the protocol to ensure datadelivery. Reliable streaming protocols provide reliable, ordereddelivery of a stream of bytes from one computer to another computer.Reliable streaming protocols ensure data delivery by managing messagetransmission and acknowledgment, dropped data segment retransmission,and delivery timeout, among other things Reliable streaming protocolscan be contrasted with “simple” or “connectionless” transmissionprotocols that do not provide reliable delivery of data segments. Onesuch example of a connectionless protocol is the User Datagram Protocol(UDP). In the UDP, there is no indication whether a data segment sent toa recipient is lost during transmission. As would be appreciated by onehaving skill in the relevant art(s) given the description herein, remoteprocedure protocol (RPC) is an application layer protocol thatimplements a communication layer protocol such as but not limited toTCP.

Embodiments herein are described with reference to TCP as an exemplaryreliable streaming protocol; however, it is within the knowledge of oneskilled in the art to identify other reference reliable streamingprotocols that are adaptable according to the teachings in thisdisclosure.

One approach to enabling data communication between full-duplex capableserver 102 and full-duplex capable client 112 is to establishfull-duplex bi-directional communication between full-duplex capableserver 102 and full-duplex capable client 112. For example, full-duplexbi-directional communication enables data streaming between fall-duplexcapable server 102 and full-duplex capable client 112 over a singleprotocol connection, as opposed to the conventional approach ofbi-directional communication on separate protocol connections.

Full-Duplex Bi-Directional Communication

FIG. 2 depicts an example full-duplex bi-directional communicationsystem 200 in which embodiments, or portions thereof, may beimplemented. System 200 includes full-duplex capable server 102,full-duplex capable client 112, network 108, a client application 280, aserver application 230, and single TCP connection 130. Full-duplexcapable server 102 includes a server communication stack 210 and aserver proxy 220. Full-duplex capable client 112 includes a clientcommunication stack 260 and a client proxy 270. Network 108 includesnetwork proxy 250.

In an embodiment, full-duplex capable client 112 and full-duplex capableserver 102 engage in full-duplex bi-directional communication oversingle TCP connection 130 using an RPC communication protocol. In orderto make such bi-directional communication possible without breaking thesemantics of the RPC protocol, the RPC protocol is altered through aprotocol extension that inserts the necessary semantics to allow suchbi-directional communication. Specifically, the full-duplexbi-directional communication over single TPC connection 130 follows theRPC communication protocol semantics, such as basic HTTPrequest-response semantics, with the added semantics supportingbi-directional communication. In this manner, full-duplex bidirectionalcommunication over single TCP connection 130 using HTTP providessimultaneous streaming between full-duplex capable server 102 andfull-duplex capable client 112.

For example, full-duplex capable server 102 may send a response tofull-duplex capable client 112 simultaneously with full-duplex capableclient 112 sending a request to full-duplex capable server 102. Bothfull-duplex capable server 102 and full-duplex capable client 112 areexplicitly designed to support simultaneous streaming. Standard HTTP isnot sufficient to alone support full-duplex bi-directional communicationover single TCP connection 130. The additional protocol requirementsenable fall-duplex capable server 102 and full-duplex capable client 112to effectively engage in full-duplex bidirectional communication oversingle TCP connection 130 using a RPC protocol such as HTTP.

Full-duplex capable client 112 initiates a request data stream over aRPC based communication protocol by way of single TCP connection 130 tofull-duplex capable server 102 via network 108. Full-duplex capableserver 102 receives the request data stream. Full-duplex capable server102 responds to the request data stream by initiating a response datastream. Full-duplex capable server 102 streams the response data streamover a RPC based communication protocol by way of single TCP connection130 to full-duplex capable client 112 via network 108. Full-duplexcapable client 112 receives the response data stream. The request datastream and the response data stream operate simultaneously over singleTCP connection 130 establishing full-duplex bi-directionalcommunication.

In an embodiment, client application 280 and server application 230communicate with fall-duplex capable client 112 and full-duplex capableserver 102, respectively. As noted above, full-duplex capable client 112may be implemented on a personal computer, handheld computer, personaldigital assistant, smart phone, a mobile telephone, a game console, aset-top box, and the like. As would be appreciated by one having skillin the relevant art(s) given the description herein, client application280 includes an application that operates on any of the above. As wouldbe appreciated by one having skill in the relevant art(s) given thedescription herein, server application 230 includes an application thatoperates on any of the above.

Client application 280 initiates a request to full-duplex capable client112 to communicate with server application 230. Full-duplex capableclient 112 initiates a request data stream that contains the request ofclient application 280 to full-duplex capable server 102. Full-duplexcapable server 102 receives the request data stream and delivers therequest from client application 280 in real-time to server application230. Server application 230 processes the request and sends a responseto the request to full-duplex capable server 102. Full-duplex capableserver 102 initiates the response data stream that contains the responseto the request sent by server application 230. Full-duplex capableserver 102 streams the response data stream to full-duplex capableclient 112. Full-duplex capable client 112 receives the response datastream and delivers the response from server application 230 to clientapplication 280. The request data stream and the response data streamoperate simultaneously over single TCP connection 130 establishingfull-duplex bi-directional communication.

In an embodiment, full-duplex bi-directional communication betweenfull-duplex capable client 112 and full-duplex capable server 102 may becompletely controlled by server application 230. Full-duplexbi-directional communication may be limited to clients that have beenexplicitly identified by full-duplex capable server 102. Clientapplication 280 that is not controlled by server application 230 may berequired to advise of its capability to engage in full-duplexbi-directional communication by streaming URL parameters and/or headersto server application 230. Client application 280 that is not controlledby server application 230 and/or not verified as having full-duplexbi-directional communication capability by server application 230 shouldnot be engaged in fall-duplex bi-directional communication.

In an embodiment, full-duplex communication between full-duplex capableclient 112 and full-duplex capable server 102 may be established whenclient proxy 270, network proxy 250, and server proxy 220 allow suchfull-duplex communication. As would be appreciated by one having skillin the relevant art(s) given the description herein, a proxy acts as anintermediary for requests between communication devices such as but notlimited to clients, servers, or networks seeking to use each others'resources. A proxy relies on filtering rules for allowing or disallowingaccess to the communication device that the proxy represents. Forexample, a proxy may use filtering rules that allow requests based on acommunication protocol such as HTTP to access the communication devicebut disallow other protocol based requests.

Network proxy 250, server proxy 220, and client proxy 270 includefiltering rules that allow data streams based on a RPC basedcommunication protocol to stream into network 108, full-duplex capableserver 102, and full-duplex capable client 112, respectively. If thedata streams are based on a communication protocol different than RPC,then network proxy 250, server proxy 220, and client proxy 270 may denythe data streams access to network 108, full-duplex capable server 102,and full-duplex capable client 112, respectively. However, the requestand response data streams generated by full-duplex capable client 112and full-duplex capable server 102 are a RPC based communicationprotocol. As a result, network proxy 250, server proxy 220, and clientproxy 270 allow the request and the response data streams to flow freelybetween full-duplex capable client 112 and full-duplex capable server102 via network 108.

In an embodiment, network proxy 250, server proxy 220, and client proxy270, may disallow an early response from full-duplex capable server 102.Network proxy 250, server proxy 220, and client proxy 270 may alsobuffer requests from full-duplex capable client 112 and responses fromfull-duplex capable server 102. In buffering, client application 280and/or server application 230 may switch from full-duplex bi-directionalcommunication to a different protocol that uses two connections ratherthan single TCP connection 130. Full-duplex capable client 112 andfull-duplex capable server 102 may implement such fall back techniquessuch as polling. Full-duplex capable client 112 may also implement thefall back technique of waiting for the initial response from full-duplexcapable server 102 for a short time-out period.

In an embodiment, full-duplex capable client 112 and full-duplex capableserver 102 each have a communication interface. Client communicationstack 260 acts as a communication interface for full-duplex capableclient 112. Server communication stack 210 acts as a communicationinterface for full-duplex capable server 102.

Client communication stack 260 of full-duplex capable server 102receives the request generated by client application 280. Clientcommunication stack 260 initiates the request data stream over singleTCP connection 130 via network 108 to server communication stack 210.The request data stream generated by full-duplex capable client 112 isbased on a RPC based communication protocol so network proxy 250 andserver proxy 220 allow the request data stream to flow through network108 and access full-duplex capable server 102. Server communicationstack 210 receives the request data stream from full-duplex capableclient 112 and transfers the request data stream to server application230.

Server application 230 sends a response to the request data stream toserver communication stack 210. Server communication stack 210 initiatesthe response data stream over single TCP connection 130 via network 108to client communication stack 260. The response data stream generated byfull-duplex capable server 102 is based on a RPC based communicationprotocol so network proxy 250 and client proxy 270 allow the responsedata stream to flow through network 108 and access full-duplex capableclient 112. Client communication stack 260 receives the response datastream and sends the response to client application 280. The requestdata stream and the response data stream operate simultaneously oversingle TCP connection 130 establishing full-duplex bi-directionalcommunication. Server communication stack 210 and client communicationstack 260 provide messaging support and required delivery guarantees.

Full-Duplex Bi-Directional Communication Semantics

FIG. 3 depicts an example full-duplex bi-directional communicationsystem 300 in which embodiments, or portions thereof, may beimplemented. System 300 includes full-duplex capable client 112 andfull-duplex capable server 102. Full-duplex capable client 112 andfull-duplex capable server 102 engage in a series of data exchanges toestablish full-duplex bi-directional communication.

In an embodiment, full-duplex capable client 112 and full-duplex capableserver 102 establish full-duplex communication by following a series offull-duplex bi-directional communication semantics. Full-duplex capableclient 112 initiates full-duplex communication with fall-duplex capableserver 102 by sending an initial handshake request 310 to full-duplexcapable server 102. Full-duplex capable server 102 either accepts orrejects initial handshake request 310. If full-duplex capable server 102rejects initial handshake request 310, full-duplex communication betweenfull-duplex capable client 112 and full-duplex capable server 102 fails.

If full-duplex capable server 102 accepts initial handshake request 310from full-duplex capable client 112, then full-duplex communicationbetween full-duplex capable server 102 and full-duplex capable client112 is established. Full-duplex capable server 102 accepts initialhandshake request 310 by responding with initial handshake acceptance320. Once full-duplex capable client 112 receives initial handshakeacceptance 320, full-duplex communication between full-duplex capableclient 112 and full-duplex capable server 102 is finalized.

In an embodiment, full-duplex communication between full-duplex capableclient 112 and full-duplex capable server 102 may be established by thecompletion of a handshake based on HTTP semantics. Initial handshakerequest 310 follows HTTP semantics. Full-duplex capable client 112 sendsa HTTP request to full-duplex capable server 102. The HTTP request isfollowed by a body completing initial handshake request 310. Initialhandshake acceptance 320 also follows HTTP semantics where full-duplexcapable server 102 responds to initial handshake request 310 by sendingthe response headers to full-duplex capable client 112. Once full-duplexcapable client 112 has received the header from full-duplex capableserver 102, the HTTP based handshake has been completed and full-duplexcommunication between full-duplex capable client 112 and full-duplexcapable server 102 is established.

In an embodiment, data streaming between full-duplex capable client 112and fall-duplex capable server 102 is initiated following the receipt ofinitial handshake acceptance 320 by full-duplex capable client 112.Full-duplex capable client 112 initiates request stream 330 and streamsrequest stream 330 to full-duplex capable server 102. Full-duplexcapable server 102 receives request stream 330 from full-duplex capableclient 112 and, before completion of request stream 330, responds bystreaming response stream 340 to full-duplex capable client 112.Full-duplex bi-directional communication 350 may be established whenfull-duplex capable client 112 streams request stream 330 to full-duplexcapable server 102 and full-duplex capable server 102 streams responsestream 340 to full-duplex capable client 112 over single TCP connection130 simultaneously.

In an embodiment, full-duplex bi-directional communication 350 continuesbetween full-duplex capable client 112 and full-duplex capable server102 until full-duplex capable client 112 terminates request stream 330.The terminating of request stream 330 by full-duplex capable client 112terminates full-duplex bi-directional communication 350 but does notterminate the communication link. Full-duplex capable client 112continues to receive response stream 340 from full-duplex capable server102 as long as full-duplex capable server 102 continues to streamresponse stream 340. Full-duplex communication is terminated whenfull-duplex capable server 102 terminates streaming response stream 340and full-duplex capable client 112 receives response stream termination370 signifying the end of response stream 340.

Before full-duplex capable server 102 receives request streamtermination 360 signifying the end of request stream 330, full-duplexcapable server 102 may terminate response stream 340. Full-duplexcapable server 102 terminating response stream 340 before receivingrequest stream termination 360 is considered an illegal state in HTTPwhere request stream 330 continues after response stream 340 has beenterminated. Therefore, full-duplex capable client 112 may terminaterequest stream 330 immediately upon receiving response streamtermination 370 from full-duplex capable server 102 signifying the endof response stream 340.

In an embodiment, full-duplex bi-directional communication 350 betweenfull-duplex capable client 112 and full-duplex capable server 102 isestablished over a RPC based communication protocol that may includeHTTP. In such an embodiment, full-duplex bi-directional communication350 follows standard HTTP semantics. Following the success of initialhandshake request 310 by full-duplex capable server 102 that typicallyinvolves the acceptance of the complete headers, full-duplex capableclient 112 initiates request stream 330 to full-duplex capable server102. Following HTTP semantics, full-duplex capable server 102 refuses togenerate response stream 340 until full-duplex capable server 102 hasreceived a portion of request stream 330 from full-duplex capable client112.

Once full-duplex capable server 102 has received request stream 330 fromfull-duplex capable client 112, full-duplex capable server 102 initiatesresponse stream 340 to full-duplex capable client 112. Full-duplexcapable server 102 refrains from terminating the streaming of responsestream 340 until full-duplex capable server 102 has received requeststream termination 360 signifying the end of request stream 330 fromfull-duplex capable client 112. Full-duplex capable client 112 continuesto receive response stream 340 from full-duplex capable server 102 untilfull-duplex capable client 112 receives response stream termination 370from full-duplex capable server 102 signifying the end of responsestream 340.

In an embodiment, full-duplex bi-directional communication 350 betweenfull-duplex capable client 112 and full-duplex capable server 102 isterminated based on error conditions. Specifically, full-duplex capableclient 112 terminates request stream 330 when full-duplex capable client112 receives an error response in response stream 340 from full-duplexcapable server 102, thereby terminating full-duplex bi-directionalcommunication 350.

Full-duplex capable client 112 terminates request stream 330 whenfull-duplex capable client 112 is incapable of streaming request stream330 or when request stream 330 times out, thereby terminatingfull-duplex bi-directional communication 350. Likewise, full-duplexcapable server 102 terminates response stream 340 when full-duplexcapable server 102 is incapable of streaming response stream 340, orwhen response stream 340 times out, thereby terminating full-duplexbi-directional communication 350.

In an embodiment, full-duplex bi-directional communication 350 betweenfull-duplex capable client 112 and full-duplex capable server 102 maysupport pipelining. Full-duplex capable client 112 and full-duplexcapable server 102 may support pipelining by maintaining persistentconnections. Full-duplex capable client 112 and full-duplex capableserver 102 maintain persistent connections by using the same single TCPconnection 130 rather interchanging between different TCP connectionswhen engaging in full-duplex bi-directional communication 350.Full-duplex capable client 112 when generating request stream 330 maymake single TCP connection 130 unavailable for pipelined requests.Full-duplex capable server 102 continuing response stream 340 after thetermination of request stream 330 may prevent any pipelined requestsfrom being processed.

System 400

FIG. 4 is an example system architecture 400 in which embodiments of thepresent invention or portions thereof, may be implemented. Systemarchitecture 400 includes client initialization module 402 coupled toclient application 280. Client enablement module 408 may also be coupledto client application 280.

Server delivery module 414 may be coupled to server application 230.Server streaming module 416 may also be coupled to server application230. While the embodiment depicted in FIG. 4 shows client application280 coupled to client initialization module 402 and client enablementmodule 408 and server application 230 coupled to server delivery module414 and server streaming module 416, it is important to note thatembodiments can be used to exchange data between a variety of differenttypes of computer-implemented data sources, systems and architectures,such as a networked cloud based architecture.

Full-duplex capable client 112 includes client communication stack 260,client initialization module 402 that initializes initial handshakerequest 310, client streaming module 404 that generates request stream330, client acceptance module 406 that receives response stream 340, andclient enablement module 408. Full-duplex capable server 102 includesserver communication stack 210, server connection module 410 thatreceives initial handshake request 310, server acceptance module 412that receives request stream 330, server delivery module 414 thattransfers request stream 330, server streaming module 416 that receivesserver response 470 and generates response stream 340, and serverenablement module 418. Full-duplex capable client 112 and full-duplexcapable server 102 communicate over single TCP connection 130.

In general, full-duplex bi-directional communication between full-duplexcapable client 112 and full-duplex capable server 102 operates asfollows. Client application 280 supplies client request 420, whereclient request 420 is a request to initialize communication with serverapplication 230. Client initialization module 402 receives clientrequest 420 from client application 280. Based on client request 420,client initialization module 402 generates initial handshake request 310to initialize full-duplex communication over single TCP connection 130between full-duplex capable client 112 and full-duplex capable server102. Communication links such as single TCP connection 130 may be reusedacross streaming RPC connections.

In an embodiment, client communication stack 260 and servercommunication stack 210 may be interfaces for full-duplex capable client112 and full-duplex capable server 102, respectively. Clientcommunication stack 260 receives initial handshake request 310 fromclient initialization module 402 and sends initial handshake request 310to full-duplex capable server 102 over single TCP connection 130. Servercommunication stack 210 receives initial handshake request 310 fromfull-duplex capable client 112 over single TCP connection 130. Servercommunication stack 210 sends initial handshake request 310 to serverconnection module 410. Server connection module 410 accepts initialhandshake request 310 finalizing the handshake between full-duplexcapable client 112 and full-duplex capable server 102 over single TCPconnection 130.

Once the handshake between full-duplex capable client 112 andfull-duplex capable server 102 over single TCP connection 130 has beenfinalized, client streaming module 404 generates request stream 330 thatcontains client request 420. Client communication stack 260 receivesrequest stream 330 from client streaming module 404 and streams requeststream 330 over single TCP connection 130 to full-duplex capable server102. Server communication stack 210 receives request stream 330 fromfull-duplex capable client 112. Server communication stack 210 sendsrequest stream 330 to server acceptance module 412. Server acceptancemodule 412 accepts request stream 330.

In an embodiment, server acceptance module 412 sends request stream 330to server delivery module 414. Server delivery module 414 transfersrequest stream 330 to server application 230. Server application 230receives request stream 330 containing client request 420 and respondsto client request 420 with server response 470. Server application 230sends server response 470 to server streaming module 416. Serverstreaming module 416 receives server response 470 and generates responsestream 340 that contains server response 470. Server streaming module416 streams server response stream 340 to server enablement module 418.

In an embodiment, server enablement module 418 enables a full-duplexbi-directional communication stream over single TCP connection 130 whenserver enablement module 418 streams response stream 340 to servercommunication stack 210. Server communication stack 210 in turn sendsresponse stream 340 over single TCP connection 130 to full-duplexcapable client 112 as full-duplex capable client 112 streams requeststream 330 to full-duplex capable server 102 enabling full-duplexbi-directional communication.

In an embodiment, client communication stack 260 receives responsestream 340 from full-duplex capable server 102 over single TCPconnection 130. Client communication stack 260 sends response stream 340to client acceptance module 406. Client acceptance module 406 acceptsresponse stream 340 while full-duplex capable client 112 streams requeststream 330 to full-duplex capable server 102. Client acceptance modulesends server response stream 340 to client enablement module 308. Clientenablement module 308 enables full-duplex bi-directional communicationbetween full-duplex capable client 112 and full-duplex capable server102 when response stream 340 streams to full-duplex capable client 112and request stream 330 streams to full-duplex capable server 102simultaneously over single TCP connection 130.

Modules may be used by full-duplex capable client 112 and full-duplexcapable server 102. As referred to herein, a module may be any type ofprocessing (or computing) device having one or more processors. Forexample, a module can be a workstation, mobile device, computer, clusterof computers, set-top box, or other devices having at least oneprocessor. In an embodiment, multiple modules may be implemented on thesame processing device. Software may include one or more applicationsand an operating system. Hardware can include, but may not be limitedto, a processor, memory, and/or graphical user interface display.

Method 500

FIG. 5 illustrates a flowchart of an exemplary method 500 ofestablishing full-duplex bi-directional communication with a full-duplexcapable client. As shown in FIG. 5, method 500 begins at step 510, whenthe full-duplex capable client initiates full-duplex communication witha server. For example, as shown in FIG. 1 and FIG. 3, full-duplexcapable client 112 initiates full-duplex communication over single TCPconnection 130 between full-duplex capable client 112 and full-duplexcapable server 102 via network 108. Full-duplex capable client 112 isconfigured to engage full-duplex capable server 102 by sending initialhandshake request 310 to full-duplex capable server 102. Step 510 may beperformed by, for example, client initialization module 402. Once step510 is complete, method 500 proceeds to step 520.

At step 520, the full-duplex capable client streams a client requeststream to the server. For example, as shown in FIG. 1 and FIG. 3,full-duplex capable client 112 streams request stream 330 to full-duplexcapable server 102 following initial handshake acceptance 320 of initialhandshake request 310 by full-duplex capable server 102 via network 108over single TCP connection 130. Step 520 may be performed by, forexample, client streaming module 404. Once step 520 is complete, method500 proceeds to step 530.

At step 530, the full-duplex capable client accepts a response streamfrom the server. For example, as shown in FIG. 1 and FIG. 3, full-duplexcapable client 112 accepts response stream 340 from full-duplex capableserver 102 over single TCP connection 130 while full-duplex capableclient 112 streams request stream 330 over single TCP connection 130.Step 540 may be performed by, for example, client acceptance module 406.Once step 530 is complete, method 500 proceeds to step 540.

At step 540, the full-duplex bi-directional communication stream isenabled over the remote procedure call based communication protocol. Forexample, as shown in FIG. 1 and FIG. 3, the full-duplex bi-directionalcommunication 350 is enabled over the remote procedure call basedcommunication protocol when request stream 330 and response stream 340communicate over single TCP connection 130 simultaneously. Step 540 maybe performed by, for example, client enablement module 408. When step540 is complete, method 500 ends.

Embodiments can work with software, hardware, and/or operating systemimplementations other than those described herein. Any software,hardware, and operating system implementations suitable for performingthe functions described herein can be used. Embodiments are applicableto both a client and to a server or a combination of both.

Method 600

FIG. 6 illustrates a flowchart of an exemplary method 600 forestablishing full-duplex bi-directional communication with a full-duplexcapable server. As shown in FIG. 6, method 600 begins at step 610, wherefull-duplex communication is finalized over a single protocol connectionbetween the full-duplex capable server and a client via a network. Forexample, as shown in FIG. 1 and FIG. 3, full-duplex communication isfinalized over single TCP connection 130 between full-duplex capableserver 102 and full-duplex capable client 112 via network 108.Full-duplex capable server 102 is configured to accept initial handshakerequest 310, from full-duplex capable client 112. Step 610 may beperformed by, for example, server connection module 410. Once step 610is complete, method 600 proceeds to step 720.

At step 620, the full-duplex capable server accepts a request streamover the single protocol connection. For example, as shown in FIG. 1 andFIG. 3, full-duplex capable server 102 accepts request stream 330 oversingle TCP connection 130. Step 620 may be performed by, for example,server acceptance module 412. Once step 620 is complete, method 600proceeds to step 630.

At step 630, the request stream received by the full-duplex capableserver is transferred to a server application. For example, as shown inFIG. 1 and FIG. 2 and FIG. 3, request stream 330 received by full-duplexcapable server 102 is transferred to server application 230. Step 630may be performed by, for example, server delivery module 414. Once step630 is complete, method 600 proceeds to step 740.

At step 640, the full-duplex capable server streams a server responsestream to the client. For example, as shown in FIG. 1 and FIG. 3,full-duplex capable server 102 streams response stream 340 tofull-duplex capable client 112 that comprises of an application responseto request stream 330 by server application 230 via network 108 oversingle TCP connection 130. Step 640, may be performed by, for example,server streaming module 416. Once step 640 is complete, method 600proceeds to step 650.

At step 650, a full-duplex bi-directional communication stream isenabled over the remote procedure call based communication protocol. Forexample, as shown in FIG. 1 and FIG. 3, full-duplex bi-directionalcommunication 350 is enabled over the remote procedure call basedcommunication protocol when response stream 340 and request stream 330use single TCP connection 130, simultaneously. When step 650 iscomplete, method 600 ends.

Embodiments can work with software, hardware, and/or operating systemimplementations other than those described herein. Any software,hardware, and operating system implementations suitable for performingthe functions described herein can be used. Embodiments are applicableto both a client and to a server or a combination of both.

Conclusion

Embodiments can work with software, hardware, and/or operating systemimplementations other than those described herein. Any software,hardware, and operating system implementations suitable for performingthe functions described herein can be used. Embodiments are applicableto both a client and to a server or a combination of both.

The Brief Summary and Abstract sections may set forth one or more butnot all exemplary embodiments as contemplated by the inventors, andthus, are not intended to limit the present invention and the appendedclaims in any way.

Embodiments have been described above with the aid of functional blocksillustrating the implementation of specified functions and relationshipsthereof. The boundaries of these functional blocks have been arbitrarilydefined herein for the convenience of the description. Alternateboundaries can be defined so long as the specified functions andrelationships thereof are appropriately performed.

The foregoing description of specific embodiments will so fully revealthe general nature of the invention that others can, by applyingknowledge within the skill of the art, readily modify and/or adapt forvarious applications such specific embodiments, without undueexperimentation, without departing from the general concept of thepresent invention. Therefore, such adaptations and modifications areintended to be within the meaning and range of equivalents of thedisclosed embodiments, based on the teaching and guidance presentedherein. It is to be understood that the phraseology or terminologyherein is for the purpose of descriptions and not of limitation, suchthat the terminology or phraseology of the present specification is tobe interpreted by the skilled artisan in light of the teachings andguidance.

The breadth and scope of the present invention should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

1. A computer implemented method for providing a full-duplex capableclient to establish a full-duplex bi-directional communication streamover a remote procedure call based communication protocol by way of asingle protocol connection, comprising: initiating, by the full-duplexcapable client, full-duplex communication over a single protocolconnection between the full-duplex capable client and a server via anetwork, wherein the full-duplex capable client is configured to engagethe server by sending an initial handshake to the server; streaming aclient request stream by the full-duplex capable client to the serverfollowing an acceptance of the initial handshake by the server via thenetwork over the single protocol connection; accepting, by thefull-duplex capable client, a response stream from the server over thesingle protocol connection while the full-duplex capable client streamsthe client request stream over the single protocol connection; andenabling, by the full-duplex capable client, the full-duplexbi-directional communication stream over the remote procedure call basedcommunication protocol when the client request stream and the responsestream communicate over the single protocol connection simultaneously.2. The method of claim 1, further comprising: terminating thefull-duplex communication over the single protocol connection with theserver when both the client request stream and the response stream havebeen discontinued.
 3. The method of claim 2, further comprising:terminating the full-duplex bi-directional communication stream bydiscontinuing the client request stream; and continuing the full-duplexbi-directional communication stream with the server over the singleprotocol connection by accepting the response stream.
 4. The method ofclaim 1, wherein the full-duplex capable client streams the clientrequest stream when a set of client proxies and a set of network proxiesread the remote procedure call based communication protocol.
 5. Themethod of claim 1, wherein the single protocol connection is a singletransmission control protocol.
 6. The method of claim 1, wherein theremote procedure call based communication protocol is a hypertexttransfer protocol.
 7. A computer implemented method for providing afull-duplex capable server to establish a full-duplex bi-directionalcommunication stream over a remote procedure call based communicationprotocol by, way of a single protocol connection, comprising: finalizingfull-duplex communication over a single protocol connection between thefull-duplex capable server and a client via a network, wherein thefull-duplex capable server is configured to accept an initial handshakefrom the client; accepting a request stream over the single protocolconnection; transferring the request stream received by the full-duplexcapable server to a server application; streaming a server responsestream to the client that comprises an application response to therequest stream by the server application via the network over the singleprotocol connection; and enabling a full-duplex bi-directionalcommunication stream over the remote procedure call based communicationprotocol when the server response stream and the request stream use thesingle protocol connection simultaneously.
 8. The method of claim 7,further comprising: refusing to stream the server response stream to theclient until the request stream has been accepted by the full-duplexcapable server; continuing full-duplex bi-directional communicationstream with the client over the single protocol connection by acceptingthe request stream; and terminating full-duplex communication over thesingle protocol connection with the client when both the server responsestream and the request stream have been discontinued.
 9. The method ofclaim 7, wherein the full-duplex capable server streams the serverrequest stream when a set of server proxies and a set of network proxiesread the remote procedure call based communication protocol.
 10. Themethod of claim 7, wherein the single protocol connection is a singletransmission control protocol.
 11. The method of claim 7, wherein theremote procedure call based communication protocol is a hypertexttransfer protocol.
 12. A system for providing a full-duplex capableclient to establish a full-duplex bi-directional communication streamover a remote procedure call (RPC) based communication protocol by wayof a single protocol connection, comprising: a client initializationmodule that initiates full-duplex RPC communication over a singleprotocol connection between the full-duplex capable client and a servervia a network, wherein the full-duplex capable client is configured toengage the server by sending an initial handshake to the server; aclient streaming module that streams a client request stream by thefull-duplex capable client to the server following an acceptance of theinitial handshake by the server via the network over the single protocolconnection; a client acceptance module that accepts a response streamfrom the server over the single protocol connection while thefull-duplex capable client streams the client request stream over thesingle protocol connection; and a client enablement module that enablesthe full-duplex bi-directional communication stream over the RPC basedcommunication protocol when the client request stream and the responsestream communicate over the single protocol connection simultaneously,wherein the client initialization module, the client streaming module,the client acceptance module and the client enablement module areimplemented in a processing device.
 13. The system of claim 12, whereinthe client streaming module is further configured to: terminatefull-duplex RPC communication over the single protocol connection withthe server when both the client request stream and the response streamhave been discontinued.
 14. The system of claim 13, wherein the clientstreaming module is further configured to: terminate the full-duplexbi-directional communication stream by discontinuing the client requeststream; and continue full-duplex RPC communication with the server overthe single protocol connection by accepting the response stream.
 15. Thesystem of claim 12, wherein the full-duplex capable client streams theclient request stream when a set of client proxies and a set of networkproxies read the RPC based communication protocol.
 16. The system ofclaim 12, wherein the single protocol connection is a singletransmission control protocol.
 17. The system of claim 12, wherein theRPC based communication protocol is a hypertext protocol.
 18. A systemfor providing a full-duplex capable server to establish a full-duplexbi-directional communication stream over a remote procedure call (RPC)based communication protocol by way of a single protocol connection,comprising: a server connection module that finalizes an initializationof full-duplex RPC communication over a single protocol connectionbetween the full-duplex capable server and a client via a network,wherein the full-duplex capable server is configured to accept aninitial handshake from the client; a server acceptance module thataccepts a request stream over the single protocol connection; a serverdelivery module that transfers the request stream received by thefull-duplex capable server to a server application; a server streamingmodule that streams a server response stream to the client that includesan application response to the request stream by the application via thenetwork over the single protocol connection; and a server enablementmodule that enables a full-duplex bi-directional communication streamover the RPC based communication protocol when the server responsestream and the request stream use the single protocol connectionsimultaneonsly, wherein the server connection module, the serveracceptance module, the server delivery module, the server streamingmodule, and the server enablement module are implemented in a processingdevice.
 19. The system of claim 18, wherein the server streaming moduleis further configured to: disallow streaming of the server responsestream to the client until the request stream has been received by thefull-duplex capable server; terminate the full-duplex bi-directionalcommunication stream by discontinuing the server response stream;continue communication with the client over the single protocolconnection by accepting the request stream; and terminate communicationover the single protocol connection with the client when both the serverresponse stream and the request stream have been discontinued.
 20. Thesystem of claim 18, wherein the full-duplex capable server streams theserver request stream when a set of server proxies and a set of networkproxies read the RPC based communication protocol.
 21. The system ofclaim 18, wherein the single protocol connection is a singletransmission control protocol.
 22. The system of claim 18, wherein theRPC based communication protocol is a hypertext transfer protocol.